-
Notifications
You must be signed in to change notification settings - Fork 19
Release reports refactor (#1996) #1999
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
rbbeeston
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm good with this if Greg is
gregjkal
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work - one request to move a comment. Approved.
2e64269 to
d58c9c7
Compare
d58c9c7 to
39007ac
Compare
Release reports refactor (#1996)
39007ac to
a0890cb
Compare
…ews. Refined release report publishing and added locking. Limited release report dropdown list. (#2001)
0a0d111 to
669bd2b
Compare
…ration error when no Algolia info exists, Updated scheme references to use constant from settings (#1895)
669bd2b to
7d958cd
Compare
|
Tested in localhost:8000. Release report update docs (docs/release_reports.md) and buttons should be correct and function accordingly. <- Works as expected This is ready to go to stage @daveoconnor |
This is related to ticket #1996.
Makes the release reports code more readable.
Moves some processing out to celery tasks for parallelization, left items where it made more sense for developers to get querysets or objects etc. back, performance isn't the key aim.
Also adds a fix for release report generation with base path not being set correctly when generating through the admin ui.